This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
solution? cause seems to be a DNS problem not well handled by the router task
After some more research, I thought I would post my current hypothesis, in case this helps someone in the future...
My mail server was pointing it's DNS to an old DNS server. This was "on it's way out" and so my network group built a new one. However my mail server was not updated. So, it was pointing to a server that would mostly work, but sometimes not respond. This morning that old server was decommissioned, and so we found the network entry point to the old server, changed it and have our fingers crossed that this is the root cause of the problem.
IMHO this does not excuse the Domin router from trying to send an email to the A record of the Domain, instead of the MX record of the Domain.
Later you will see
27/04/2009 09:30:33 AM Router: Domain xxxxx.COM added to cache; NRPC next hop = , SMTP next hop = xxxxx.COM, Status = 0x0, Timeout = 06/05/2043 11:07:36 PM
IMHO this is a BUG in the router: it should just wait for the DNS to respond, rather than using the (wrong) domain A record.
Feedback response number WEBB7RH2C6 created by ~Vera Quetponesterikle on 04/27/2009
solution? cause seems to be a DNS problem not well handled by the router task
Return to top
. . . . . . . . . . solution? cause seems to be a DNS p... (~Vera Quetpones... 27.Apr.09) 
